<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
  <title>Borland&reg; Together&reg; 2008 Service Pack 1 Release Notes</title>
  <meta http-equiv="Content-Type"
 content="text/html; charset=iso-8859-1">
  <style>
BODY {
	MARGIN-TOP: 12pt; FONT-SIZE: 12px; MARGIN-LEFT: 12pt; COLOR: #000000; MARGIN-RIGHT: 12px; FONT-FAMILY: "Arial"
}
P {
	MARGIN-TOP: 6pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: normal; FONT-SIZE: 100%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
P.comment {
	MARGIN-TOP: 3pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: normal; FONT-SIZE: 100%; MARGIN-BOTTOM: 3pt; COLOR: silver; FONT-STYLE: normal; TEXT-ALIGN: left
}
P.sub {
	MARGIN-TOP: 0pt; DISPLAY: block; FONT-WEIGHT: normal; FONT-SIZE: 100%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
H1 {
	BORDER-TOP: activecaption groove; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: bold; FONT-SIZE: 190%; MARGIN-BOTTOM: 10pt; BORDER-LEFT: activecaption groove; COLOR: navy; FONT-STYLE: normal; TEXT-ALIGN: left
}
H2 {
	BORDER-TOP: activecaption groove; MARGIN-TOP: 20pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: bold; FONT-SIZE: 150%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
H3 {
	MARGIN-TOP: 18pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: bold; FONT-SIZE: 130%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
UL {
	MARGIN-TOP: 6pt; MARGIN-BOTTOM: 3pt; LIST-STYLE-TYPE: square
}
UL UL {
	MARGIN-TOP: 3pt; MARGIN-BOTTOM: 3pt; LIST-STYLE-TYPE: disc
}
OL {
	MARGIN-TOP: 6pt; MARGIN-BOTTOM: 3pt; MARGIN-LEFT: 42pt
}
OL OL {
	MARGIN-TOP: 3pt; MARGIN-BOTTOM: 3pt; MARGIN-LEFT: 24pt; LIST-STYLE-TYPE: disc
}
LI {
	MARGIN-TOP: 0pt; MARGIN-BOTTOM: 3pt; MARGIN-LEFT: -12pt
}
TABLE {
	BORDER-TOP: silver 1.5pt solid; MARGIN-TOP: 3pt; FONT-WEIGHT: normal; FONT-SIZE: 95%; MARGIN-BOTTOM: 10pt; MARGIN-LEFT: 5pt; BORDER-BOTTOM: silver 1.5pt solid; TEXT-ALIGN: left
}
TR {
	VERTICAL-ALIGN: top
}
TH {
	PADDING-RIGHT: 3pt; FONT-WEIGHT: bold; FONT-SIZE: 90%; VERTICAL-ALIGN: bottom; COLOR: navy
}
TD {
	PADDING-RIGHT: 3pt; BORDER-TOP: silver 1pt solid; VERTICAL-ALIGN: top
}
CODE {
	COLOR: #001095; FONT-FAMILY: courier
}
PRE {
	PADDING-RIGHT: 5pt; MARGIN-TOP: 3pt; PADDING-LEFT: 5pt; FONT-SIZE: 100%; VISIBILITY: visible; MARGIN-BOTTOM: 0pt; PADDING-BOTTOM: 3pt; MARGIN-LEFT: 5pt; OVERFLOW: visible; WIDTH: 2pc; COLOR: #001095; PADDING-TOP: 3pt; FONT-FAMILY: "Courier New"; BACKGROUND-COLOR: #f5f5f5
}
  </style>
  <meta content="MSHTML 6.00.6000.16481" name="GENERATOR">
</head>
<body>
<h1><a name="0"></a>Borland<em><i><sup>&reg;</sup></i></em> Together<em><i><sup>&reg;</sup></i></em>
2008 Service Pack 1 Release Notes</h1>
<p>Last updated: March 27, 2009</p>
<p>This file contains important information that may not appear in the
online Help. Please read this file in its entirety.</p>
<p><a href="#whats_new">What's New and Fixed in This Release </a></p>
<p><a href="#sysreq">System Requirements </a></p>
<p><a href="#InstallationInstructions">Installation Instructions </a></p>
<p><a href="#PatchInstallation">Patch Installation</a></p>
<p><a href="#licensing">Licensing</a><br>
</p>
<p><a href="#issues"><span style="text-decoration: underline;">Known
Issues and Limitations</span></a><br>
</p>
<p><a href="#Capabilities">Together Capabilities</a></p>
<p><a href="#finding_out_more">Finding Out More</a></p>
<p><a href="#getting_help">Getting assistance</a></p>
<h2><a name="whats_new"></a>What's New and Fixed in This Release</h2>
<p>This release of Together includes improvements in functionality, new
features, and fixed bugs since Together 2008. The important changes
introduced in this release are highlighted below. </p>
<p>In addition to the English-only version released in November 2008, 
this release includes localization for Japanese, German, and French.</p>
<h3>Together Modeling</h3>
<p><strong><em>Modeling and Diagrams </em></strong></p>
<ul>
  <li><strong>New (Bug 23): </strong>The Enhanced Rich Text Editor for
properties is no longer an early access feature, and can be enabled or
disabled in the Capabilities window ( <strong>Window -&gt; Preferences
-&gt; Capabilities -&gt; Advanced -&gt; Modeling -&gt; Enhanced Rich
Text Editing</strong>). This capability is enabled by default.</li>
  <li><strong>New (Bug 2261, Trk#30135):&nbsp;</strong>Ant task
provided for running OCL based Model audits/metrics. Please refer topic
    <strong>Borland Together Modeling Guide &gt; Procedures &gt; Together
Quality Assurance &gt; Running Model Audits and Metrics as Ant Tasks</strong>
in the online help for details.</li>
  <li><strong>New (Bug 2478, Trk#36928): </strong>Added ability to
choose alternative way of storing properties of packages in package
model files (default.txaPackage). This information is typically stored
in the default package diagram files (default.txvpck or
default.txvClassDiagram20). This alternative way enables keeping such
properties synchronized across the team even when package diagrams are
excluded from version controlling (with the <span
 style="font-weight: bold;">Preferences </span>-&gt; <span
 style="font-weight: bold;">Team </span>-&gt; <span
 style="font-weight: bold;">Modeling resources</span>
-&gt; <span style="font-weight: bold;">Ignore default package diagrams</span>
option). The <strong>Store package properties in package diagram files</strong>
option
can be changed from the new modeling project wizard or in the Project
Properties dialog. Because changing this option in the Project
Properties
dialog for existing project results in the one-time conversion of
affected project files, this option should be used with caution.
Note that projects switched to this alternative storage of package
properties <em>cannot be opened in earlier versions of the product</em>.</li>
  <li><strong>New (Bug 2490, Trk#27573): </strong>Provided the
ModelValidator tool that looks for the severe model problems (broken
links, duplicate uins, etc).</li>
  <li><strong>Fixed (Bug 3155, Trk#36964): </strong>UML 2.0, Behavior:
You can now use the Properties Inspector to specify multiple
pre-postconditions for behaviors.</li>
  <li><strong>New (Bug 3184): </strong>Properties inspector now saves
changes automatically when application exits.</li>
  <li><strong>Fixed (Bug 4264): </strong>UML 2.0, Sequence diagram:
Lifeline head changes its shape depending on the metaclass of the
represented classifier. Supported for Actor and Component metaclasses.</li>
  <li><strong>Fixed (Bug 4488): </strong>Issue with dependencies has
been fixed in 'UML to WSDL transformation Project' sample.</li>
  <li><strong>Fixed (Bug 4496): </strong>When you copy elements with
hyperlinks from a referenced project, the hyperlink destination is
now changed to the corresponding element in the target project.</li>
  <li><strong>Fixed (Bug 4520): </strong>Profiles, properties of enum
type: You can now localize enum literals.</li>
  <li><strong>New (Bug 4522): </strong>Added support for hidden
compartments in UML 2.0 modeling projects.</li>
  <li><strong>New (Bug 4615): </strong>Warning message describing
paste semantics is shown during copy/paste operations. A
switch is provided in <strong>Window</strong> -&gt; <strong>Preferences</strong>
-&gt; <strong>Modeling</strong> -&gt; <strong>Copy/Paste</strong>
-&gt; <strong>Show warning about relationship when elements copied</strong>
to enable or
disable the warning dialog.</li>
  <li><strong>New (Bug 4631): </strong>Scope for Profile Constraints
checking (<strong>Model</strong> -&gt; <strong>Profile</strong> -&gt; <strong>Run
Profile Constraints</strong>) now can be
specified. Available scopes are project, package, and selected resource.</li>
  <li><strong>Fixed (Bug 4717 (2382), Trk#17851): </strong>Profiles:
Initial value
of stereotype attribute is now used as default value of
corresponding stereotype-specific property.</li>
  <li><strong>Fixed (Bug 5182): </strong>The Enhanced Rich Text Editor for properties 
no longer displays double-byte characters, such as Japanese hieroglyphs, incorrectly.</li>
</ul>
<br>
<p><strong><em>EMF API and Transformations</em></strong></p>
<ul>
  <li><strong>New (Bug 2084, Trk#31091):&nbsp;</strong>EMF API:
provided ability
to get sequence numbers of message links for Sequence diagram (UML 1.4)
as well as few other properties missed earlier.</li>
  <li><strong>Fixed (Bug, 2287, Trk#33517): </strong>EMF API:
Can now set <strong>name</strong> property for
erPhysical::Relationship.</li>
  <li><strong>Fixed (Bug 4533): </strong>Classloading errors in
context of M2T transformations and plug-in dependencies were fixed. All
project imports are also considered now.</li>
  <li><strong>Fixed (Bug 4614): </strong>Control flow involving
the creation of objects with the EMF API and then placing the objects
into an existing model has been optimized to use less memory and CPU
time. In particular, this improves the performance of
model-to-text transformations.</li>
  <li><strong>Fixed (Bug 4690): </strong>Profile EMF API: Fixed issues
with handling stereotypes that extend the
uml::kernel::packages::Package.</li>
  <li><strong>Fixed (Bug 4713): </strong>Profile EMF API: Access to
derived stereotypes
is now supported. Actual stereotypes hierarchy is
now displayed in Metamodel Browser.</li>
</ul>
<br>
<p><strong><em>Source code Modeling Projects<br>
</em></strong></p>
<ul>
  <li><strong>Fixed (Bug 2643, Trk#36950): </strong>QA, ILC: An
"unused item" violation is no longer reported for types that are used
as Java5 annotation values.</li>
  <li><strong>Fixed (Bug 2783): </strong>QA audits, ILC: False ILC
violations are no longer reported for java5 generic arguments.</li>
  <li><strong>Fixed (Bug 3348, Trk#36930): </strong>There is no longer
an issue with saving changes if full resource name exceeds 256
characters because the problem with long paths on Windows platform is
fixed in JDK 1.5x.</li>
  <li><strong>Fixed (Bug 3738): </strong>C++: Together crashes when
parsing struct field with undefined type.</li>
  <li><strong>Fixed (Bug 4478): </strong>Attempt to apply pattern causes 
'Type name out of scope' error if involved elements belong to different 
source roots.</li>
  <li><strong>Fixed (Bug 4504): </strong>Diagram update after class
fields are reordered does not work correctly in
Java modeling projects.</li>
  <li><strong>Fixed (Bug 4602, Trk#36759): </strong>You can now
create a class by template in a large Java package.</li>
</ul>
<br>
<p><strong><em>Data Modeling</em></strong></p>
<ul>
  <li><strong>New (Bug 1468, Trk#36249):&nbsp;</strong>Data Modeling:
Support for Microsoft SQL Server 2005 has been added.<br>
  </li>
  <li><strong>New (Bug 3015, Trk#36955):&nbsp;</strong>Data Modeling,
MySQL: provide support for BINARY and VARBINARY types.</li>
  <li><strong>New (Bug 4450, Trk#22649):&nbsp;</strong>Data Modeling,
MySQL: Added support for "AUTO_INCREMENT" column option.</li>
</ul>
<br>
<p><strong><em>Import and Export<br>
</em></strong></p>
<ul>
  <li><strong>New (Bug 715): </strong>Together XMI Import (<strong>Import</strong>
-&gt; <strong>Modeling</strong> -&gt; <strong>XMI File</strong>) now
accepts UML models from RSA7 (
xmlns:uml="http://www.eclipse.org/uml2/2.0.0/UML") and UML2Tools
(xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML").<br>
    <strong>Note:</strong> this functionality is provided in <strong>early
access</strong>
mode.
Use it with caution and contact the support team if you
encounter issues.</li>
  <li><strong>Fixed (Bug 4508): </strong>BPEL4WS export fails with an
NPE if a None event has no Event Detail.</li>
</ul>
<br>
<p><strong><em>Document Generation<br>
</em></strong></p>
<ul>
  <li><strong>Fixed (Bug 2493, Trk#31858):&nbsp;</strong>GenDoc, RTF:
if property value contains '&lt;' and HTML tags are rendered, RTF file
is broken.</li>
  <li><strong>New (Bug 3331):&nbsp;</strong>Provided ability to set
orientation of diagram images in the Generated Documentation.</li>
  <li><strong>Fixed (Bug 4535): </strong>GenRTF: For EN locale,
controls with ARIAL font no longer appear as SansSerif.</li>
  <li><strong>Fixed (Bug 4544, Trk#31858): </strong>genhtml.cmd: -d
option is ignored if it is the first or the only option passed to
genhtml and no projects are specified.</li>
  <li><strong>Fixed (Bug 4545): </strong>genhtml.cmd: Use is only
generated if the <strong>-use</strong> option is passed.</li>
</ul>
<h3>General</h3>
<ul>
  <li>Eclipse platform updated to Eclipse 3.4.1 SDK.</li>
  <li>Localization for Japanese, German, and French has been added.</li>
</ul>
<p><a href="#top">Back to top</a></p>
<h3>Integrations</h3>
<p>Unlike Together 2006 R2, Together 2008 Service Pack 1 (SP1) does not
include
integrations
with version control systems (StarTeam&reg;, ClearCase) and requirement
management products (CaliberRM&#8482;, RequisitePro). These integrations
should be available separately from Borland. The Together 2008 SP1 help
still includes information about these integrations. However, newer
versions of integrations may have some changes in functionality, so it
is recommended that you check the release notes that are provided with
each integration package.</p>
<p><a href="#top">Back to top</a></p>
<h2><a name="sysreq"></a>System Requirements/Prerequisites</h2>
<p>Following are the system requirements for installing and running
Borland Together 2008 SP1:</p>
<table border="1" cellpadding="0" cellspacing="0" width="95%">
  <tbody>
    <tr valign="top">
      <th width="9%"><b>Resources</b></th>
      <th width="46%"><b>Requirements</b></th>
      <th width="45%"><b>Notes</b></th>
    </tr>
    <tr bgcolor="#cccccc" valign="top">
      <td colspan="3"><b>Hardware</b></td>
    </tr>
    <tr valign="top">
      <td height="18" width="9%">CPU </td>
      <td height="18" width="46%">Intel<em><i><sup>&reg;</sup></i></em>
Pentium<em><i><sup>&reg;</sup></i></em> 4 1GHz (or compatible)</td>
      <td height="18" width="45%">Intel<em><i><sup>&reg;</sup></i></em>
Pentium<em><i><sup>&reg;</sup></i></em> 4 2.8 GHz or more recommended</td>
    </tr>
    <tr valign="top">
      <td width="9%">Memory</td>
      <td width="46%">1 GB minimum</td>
      <td width="45%">2 GB is recommended. For optimal performance when
working with large-scale projects, you might need to adjust the JVM
heap setting in in the <strong>Together.ini</strong>, <strong>.bat</strong>,
      <strong>.cmd</strong>, or <strong>.sh</strong> files found in
the <strong>eclipse </strong>subfolder of the Together installation
folder. For more information, refer to the Sun<em><i><sup>&reg;</sup></i></em>
FAQ: <a href="http://java.sun.com/docs/hotspot/PerformanceFAQ.html">http://java.sun.com/docs/hotspot/PerformanceFAQ.html</a>.</td>
    </tr>
    <tr valign="top">
      <td width="9%">Disk Space</td>
      <td width="46%">1.4 GB</td>
      <td width="45%">Approximately 600 MB of this space is required
for temporary installation files and will be freed after the
installation is finished.</td>
    </tr>
    <tr valign="top">
      <td width="9%">Video</td>
      <td width="46%">High color mode, 1024x768</td>
      <td width="45%">Recommended resolution: 1600x1200</td>
    </tr>
    <tr valign="top">
      <td width="9%">CD Drive</td>
      <td width="46%">Optional</td>
      <td width="45%">Necessary if installing from CD.</td>
    </tr>
    <tr bgcolor="#cccccc" valign="top">
      <td colspan="3"><b>Software</b></td>
    </tr>
    <tr valign="top">
      <td width="9%">Operating system</td>
      <td width="46%">Microsoft Windows Vista, Microsoft Windows XP Pro
with Service Pack 2<br>
Red Hat Enterprise Linux 4 update 2, x86-32 <br>
SUSE Linux Enterprise Server 10, x86-32 <br>
Solaris 10 SPARC, GTK<br>
Mac OS X 10.4, Universal, Carbon</td>
      <td width="45%">
      <p>&nbsp;</p>
      </td>
    </tr>
    <tr valign="top">
      <td width="9%">IDE Platform</td>
      <td width="46%">Eclipse SDK 3.4.1</td>
      <td width="45%">Unless you are installing to an existing Eclipse
instance, the required version of Eclipse platform is automatically
installed with Together. You do not have to download and install it
yourself. Otherwise, at least the Eclipse SDK&nbsp;package of the
specified version is required. </td>
    </tr>
    <tr valign="top">
      <td width="9%">Java Platform</td>
      <td width="46%">Sun<em><i><sup>&reg;</sup></i></em> J2SE 5.0
Update 14</td>
      <td width="45%">The required version of Java Runtime Environment
is automatically installed with Together. You do not have to download
and install it yourself.</td>
    </tr>
    <tr valign="top">
      <td>Eclipse components and projects</td>
      <td>
      <div>
      <ul>
        <li>Eclipse 3.4.1 SDK </li>
        <li>EMF SDK 2.4.1 (EMF + SDO + XSD) </li>
        <li>UML2 SDK 2.2.1</li>
        <li>GEF SDK 3.4.1</li>
        <li>OCL SDK 1.2.2</li>
        <li>EMF Transaction SDK 1.2.2</li>
        <li>GMF SDK 2.1.2</li>
        <li>GMF Experimental SDK 2.1.2</li>
        <li>UML2 Tools SDK 0.8.1 <br>
        </li>
        <li>Operational QVT SDK 1.0.1</li>
        <li>CDT SDK 5.0.1</li>
        <li>Birt 2.3.1 (DTP 1.6.1, WTP&nbsp;WST 3.0.2)</li>
      </ul>
      </div>
      </td>
      <td>The required versions of Eclipse components and projects are
automatically installed with Together unless you are installing to an
existing Eclipse instance or use advanced install options and install
from alternative update sites. In the latter case, if you experience
problems with inconsistent configurations please contact the support
team for assistance.</td>
    </tr>
    <tr valign="top">
      <td>Eclipse language packs</td>
      <td>
      <div>
      <ul>
        <li>Eclipse Platform (BabelLanguagePack-eclipse-&lt;locale&gt;3.4.0.v*.zip)</li>
        <li>CDT (BabelLanguagePack-tools.cdt-&lt;locale&gt;3.4.0.v*.zip)</li>
        <li>MDT (BabelLanguagePack-modeling.mdt-&lt;locale&gt;3.4.0.v*.zip)</li>
      </ul>
      </div>
      </td>
      <td>The versions of language packs available from the <A HREF=http://www.eclipse.org/babel/>Babel project</A>
immediately preceding the product release are bundled with Together and automatically 
installed during installation. If necessary, you can download a newer version of 
language packs, unpack them to a local folder prior to installation, and specify an additional 
installer option to pick that folder up during installation. Refer to the Installation 
Instructions section below for details.</td>
    </tr>
    <tr valign="top">
      <td width="9%">Web Browser</td>
      <td width="46%">Any web browser that supports frames</td>
      <td width="45%">Microsoft Internet Explorer 6.0 or later is
recommended on Windows systems. </td>
    </tr>
    <tr bgcolor="#cccccc" valign="top">
      <td colspan="3"><b>Other</b></td>
    </tr>
    <tr valign="top">
      <td width="9%">SVG Viewer</td>
      <td colspan="2">Adobe SVG viewer version 3.0 or later. Follow the
link to download this viewer from Adobe web site:<br>
      <a href="http://www.adobe.com/svg/viewer/install/mainframed.html">http://www.adobe.com/svg/viewer/install/mainframed.html</a>.</td>
    </tr>
  </tbody>
</table>
<p><a href="#top">Back to top</a></p>
<h2><a name="InstallationInstructions" id="InstallationInstructions"></a>Installation
Instructions</h2>
<p>Download the Together 2008 SP1 installer for your platform and then
run
the installer.<br>
The installer has been revised to leverage the new functionality of <a
 href="http://wiki.eclipse.org/Equinox_p2_Getting_Started">Eclipse p2</a>,
so product features and plug-ins are installed in the <strong>./dropins/together</strong>
subfolder of installation target directory. <br>
<br>
<b>Note:</b> Unlike previous versions, there is no Eclipse SDK selector
page in the Together 2008 SP1 installer. However, an existing Eclipse
directory can be selected as the Together installation directory, as
long as it is an instance of Eclipse 3.4.1 SDK or one of its
maintenance
updates. Otherwise, an error dialog will appear (<strong>Install folder
contains incorrect Eclipse SDK. Together 2008 SP1 requires Eclipse SDK
version 3.4.1 or its minor updates. Please choose other install folder</strong>).<br>
<br>
<b>Note:</b> An existing directory containing the previously installed English-only version
of Together 2008 SP1 can be selected as the Together installation directory. In this case, only 
additional localization related components and files will be added to the existing 
installation. However, note that when you uninstall the product after it has been installed this 
way, all content related to Together is removed at once.</p>
<h3>Additional Installation Options</h3>
<p>If you want to specify additional installation options (for example, administrators with large networked systems might want to install Together silently), 
or use
a newer version of language packs from the Eclipse Babel project, 
place the <strong>installer.properties</strong> file 
in the directory where your installer is located. You could also specify "-f" as a
command line parameter for the installation binary file: -f
&lt;fullPathTo File&gt;. An example of the <strong>installer.properties
</strong>file is shown below: </p>
<p>#<br>
# Destination directory to install Together<br>
# <br>
USER_INSTALL_DIR=/home/test/TestInst.silent <br>
# <br>
# Installer mode silent/console/Swing/AWT<br>
# <br>
INSTALLER_UI=silent<br>
# <br>
# Uncomment to specify a folder with unpacked Babel Eclipse language packs zips<br> 
# if you want use other Babel build than one bundled with installer<br>
# <br>
#ECLIPSE.NLS.FOLDER=/home/test/eclipse.nls</p>
<p><strong>Note:</strong> If Together is installed silently, the
Together uninstall will also be silent, so be careful not to run
multiple uninstalls. </p>
<h2><a name="PatchInstallation" id="PatchInstallation"></a>Patch
Installation </h2>
<p>To install a patch for Together 2008 SP1, perform the following
steps:</p>
<p>1. Select <strong>Help</strong> -&gt; <strong>Software Updates...</strong></p>
<p>2. Select the <strong>Available Software</strong> tab.</p>
<p>3. Expand the <strong>Borland Update Site</strong> node and search
for available patches under the <strong>Together 2008 SP1 HotFixes</strong>
node. Pick the patch you need (if any), and complete the installation
following the steps suggested by the update manager.</p>
<p>Alternatively, when a path is distributed as a zip archive rather than through the update site:</p>
<p>1. Make sure Together 2008 SP1 is not running.</p>
<p>2. In your Together 2008 SP1 installation folder, create a new subfolder for the patch within the <strong>dropins</strong> subfolder. Name the folder something identifiable (for example, you could reuse the patch archive name, <strong>hotfix1</strong>).</p>
<p>3. Unpack the content of the patch archive into the subfolder you just created.</p>
<p>4. Restart Together.</p>
<p><a href="#top">Back to top</a></p>
<h2><a name="licensing"></a>Licensing</h2>
<div>To register your software and obtain an operating license, refer
to <a href="../docs/RegisteringTogether.html">Setting Up Licensing
for Borland Together</a>.<br>
<h2><a name="issues"></a>Known Issues and Limitations</h2>
<p>New issues may be identified and/or resolved after release. Please
check the latest version of the Together Release Notes at <a
 href="http://info.borland.com/techpubs/together/">Together Technical
Publications</a> page for changes to the known issues below.<br>
</p>
<h3>Modeling and Diagrams</h3>
<ul>
  <li>
    <p> (Bug 2352) When the Hide/Show dialog is used to hide
attributes in a class diagram, the performance is slow. Use the context
menu's <strong>Hide</strong> command instead of the Hide/Show dialog
to avoid this issue. </p>
  </li>
  <li>
    <p>If
the Antialiased Text and Antialiased Graphics options are selected in
the Preferences &gt; Modeling&gt; Diagram page, the elements name
labels may appear corrupted in the Overview window. </p>
  </li>
</ul>
<ul>
  <li>
    <p>On some systems, the unexpected program termination
may occur when antialiasing features for text and graphics are turned
on. Make sure you use the latest drivers for your hardware, or try to
turn antialiasing off. </p>
  </li>
</ul>
<ul>
  <li>
    <p>EMF API provides only read access to source code elements in
modeling projects. </p>
  </li>
  <li>
    <p>EMF
API does not provide the possibility to get parameters and return the
result for Operations in UML 1.4 modeling projects. </p>
  </li>
  <li>
    <p>EMF API does not provide the possibility to get the typed
elements type in UML 1.4. modeling projects. </p>
  </li>
  <li>
    <p>BPMN diagrams (graphical part - positions, colors) are not
available through the API. </p>
  </li>
</ul>
<ul>
  <li>
    <p>You can view but should not edit design diagram
files as text files. (These files are automatically created/updated by
Together and visible in the UML Explorer when the filter is off.) If
edited and saved in this manner, the diagram can be lost. </p>
  </li>
</ul>
<ul>
  <li>
    <p>BPMN simulation in step-by-step mode goes one step
further than required. The problem is caused by using the standard
DESMO-J library and should be fixed by a future release of Together.
Note that the simulation report is calculated correctly.</p>
  </li>
  <li>
    <p>(Bug 346) Navigation to source code with the <strong>Open</strong>
context menu action does not work if the diagram editor is maximized. </p>
  </li>
</ul>
<ul>
  <li>
    <p>(Bug
4688) Data Modeling, Microsoft SQL Server 2005: Secondary XML indices
are not supported. The DDL parser can navigate through the construct [
USING
XML INDEX xml_index_name [ FOR { VALUE |
PATH | PROPERTY } ] ], but there is no support in an ERDB model.</p>
  </li>
  <li>
    <p>(Bug
4451) Data modeling: The Together ER physical metamodel is a general
domain model and
supports only
"common" DDL objects (tables, views, table columns, indexes,
constraints, etc.).
It is not designed to support server-specific DDL objects such as
Oracle's SEQUENCE. You can design a UML 2.0 profile and support
objects specific to Oracle and associations between UML 2.0 and Data
Modeling projects by using hyperlinks.</p>
  </li>
</ul>
<ul>
  <li>
    <p>Patterns with some metaclasses (for example, the
TemplateSignature metaclass) cannot be applied. </p>
  </li>
</ul>
<h3>Together OCL and QVT</h3>
<ul>
  <li>
    <p>Though you can use the allInstances() OCL
operation in Constraints, code generated for this operation is
incorrect. Java runtime does not support the generated code and
currently there is no standard way to get a collection of all instances
of a given class. </p>
  </li>
  <li>
    <p>Together does not support
code generation for isSent/message (^,^^) operators. The corresponding
error message is displayed in the "Code Generation Log" view. </p>
  </li>
  <li>
    <p>OCL
parser allows only infix form for mod and div standard operations. You
can write 'a div b', 'c mod d', but not 'a.div(b)', 'c.mod(d)'. </p>
  </li>
  <li>
    <p>Together does not support OCL constraints and code generation
for UML templates. </p>
  </li>
</ul>
<ul>
  <li>
    <p>You cannot generate Java code for QVT
transformations that use profile metamodels because these metamodels do
not have Java implementations. QVT transformations that use profile
metamodels can be run in the 'Interpreted' mode. </p>
  </li>
  <li>
    <p>The
Together Modeling and DSL Toolkit features use different
implementations of the OCL and QVT engines. Normally there should be no
problems using these simultaneously, although the UI may contain a
large amount of information. It is recommended that you turn
corresponding capabilities on or off as needed (select <strong>Window</strong>
-&gt; <strong>Preferences</strong>, and then select the <strong>General</strong>
node and the <strong>Capabilities</strong>
node). The Together OCL and QVT engines are the primary engines to use
with Together models, while the QVTO and corresponding OCL engines from
Eclipse are best suited for the DSL Toolkit. Note that source artifacts
may need adjustment when migrating between these engines because these
engines have differences in syntax and behavior. </p>
  </li>
</ul>
<h3>C++/IDL Modeling Projects</h3>
<ul>
  <li>
    <p>Moving C++ classifiers into/from other classifiers is
restricted. </p>
  </li>
  <li>
    <p>Template specializations are invalidated when changing the name
of a specialized template. </p>
  </li>
  <li>
    <p>Conditional expressions in #if directive are not supported. </p>
  </li>
  <li>
    <p>Links
as comments are limited to dependency links based on the commented
simple field declarations of a pointer or object types. </p>
  </li>
  <li>
    <p>In the generated code, links are represented as pointer type
references. </p>
  </li>
  <li>
    <p>Parser blueprints for custom links recognition are not
supported. </p>
  </li>
  <li>
    <p>There
is a side effect related to the correction of unsigned modifier
processing. When it appears in a method's formal parameter type, the
method signature differs now from the one calculated in the English
version. It may invalidate references (such as hyperlinks) to affected
methods from the design part of the project created with the
English-only version of Together 2006 R2 (build #4021.2). </p>
  </li>
  <li>
    <p>C++
modeling projects do not function properly if the product is installed
in a path containing Japanese characters. Together must be installed in
a path that does not contain these characters. </p>
  </li>
</ul>
<h3>Documentation Generation and Printing</h3>
<ul>
  <li>
    <p>Printing under the Linux platform is not available because of a
known problem with the Eclipse platform. </p>
  </li>
  <li>
    <p>(Bug
4303) Icons on diagram&nbsp;elements&nbsp;that are exported to .emf
format have
black background rather than transparent backgrounds. This affects
generated RTF documentation&nbsp;where the .emf format is used for
images by
default. Consider switching to .GIF format for images in Preferences
when generating RTF&nbsp;documentation.</p>
  </li>
</ul>
<h3>Import Together Project Wizard</h3>
<ul>
  <li>
    <p>Together cannot process external roots containing
project-relative paths. </p>
  </li>
</ul>
<h3>Referenced Projects</h3>
<ul>
  <li>
    <p>When you create a Java Modeling project from Java
projects that contain cross-project references, restart Together to
make clipboard operations (Copy, Cut, and Paste) work correctly with
the imported project roots. </p>
  </li>
  <li>
    <p>Modeling
projects cannot reference non-modeling projects: you cannot add a
reference to a non-modeling project to the Model Path project property.
The existing Java modeling projects that reference Java projects might
work incorrectly. </p>
  </li>
  <li>
    <p>You can create C++
projects referencing each other, but source code elements from
referenced projects are not available in the model. You can import
design elements only. </p>
  </li>
</ul>
<h3>XMI Import/Export</h3>
<ul>
  <li>
    <p>Rational
Rose cannot import swimlanes from XMI. When activity diagrams with
swimlane elements are exported from Together using XMI, the elements do
not appear in swimlanes in Rational Rose. </p>
  </li>
  <li>
    <p>If
you use the XMI feature to import UML 1.4 (OMG) or UML 2.0, no design
diagrams will be transferred. All the imported elements will be
imported and visible in the Model Navigator. You can then include the
imported elements into diagrams. </p>
  </li>
  <li>
    <p>While
performing XMI import to UML 1.4 or Java modeling projects, 'Replace
for packages' does not work correctly. If you want the existing
packages to be replaced on import, you should either delete them before
the import process, or rename them and then you can delete old packages
and change the names of the newly created packages after the import. </p>
  </li>
</ul>
<h3>DSL Development </h3>
<ul>
  <li>
    <p><span style="font-weight: bold;">(Bug 2694):</span> Domain
Editor: Undo operation after
refactoring of model element in the Domain editor is available if you
switch selection to the DSL Explorer. However, this will only roll-back
external references updates, so you should manually rename the element
in the editor after the Undo operation. You can also use the rename
refactor action in the Project Explorer instead, where the action can
be undone. </p>
  </li>
  <li>
    <p><span style="font-weight: bold;">(Bug 2702):</span> Model
Refactoring: Model
Refactor does not support a domain&#8217;s URI mapping. So if you have
&#8216;platform:&#8217; URI mapping in your Domain model, move or rename operations
can cause unpredictable results. It is best to clear such mappings
before a move or rename operation and then restore the mappings after
the operation. </p>
  </li>
  <li>
    <p><span style="font-weight: bold;">(Bug 2935):</span> Domain
Editor: To
avoid validation warnings during domain model resource refactoring, you
should close the Domain Editor (Eclipse bug 205426). To avoid
validation warnings on model element refactoring, you should close the
affected Diagram Editor.</p>
  </li>
  <li>
    <p><span style="font-weight: bold;">(Bug 2938):</span> Allow main
refactoring even if potential references were found in read-only
resources. If Model Refactoring finds potential matches in read-only
resources, you are prompted to make these resources writeable to apply
the entire change. If a potential change of this type is not selected
in the preview, the read-only file will not be modified.</p>
  </li>
  <li>
    <p><span style="font-weight: bold;">(Bug
3336):</span> QVTO: Type conformance problems for elements from
referenced
metamodels. When a domain model uses or extends elements from another
metamodel by referencing it by its physical (resource) URI, there are
type conformance problems when parsing a QVTO transformation. You
should reference metamodels by their NS URI to avoid this problem.</p>
  </li>
</ul>

<h3>Localization</h3>
<ul>
  <li>
    <p>Because completion of the <A HREF=http://www.eclipse.org/babel/>Eclipse localization</A> did not coincide 
with shipment of Together 2008 Service Pack 1, some of the terms 
related to Eclipse might appear in English in the product. 
Similarly, some references to the Eclipse UI in the documentation 
might also be different from the language packs you are currently using. </p>
  </li>
  <li>
    <p>All features and capacities related to the DSL Toolkit 
and UML 2.1 modeling appear in English because these components 
have not been localized. UI elements will appear in English in the product 
and references to them will appear in English in the documentation. </p>
  </li>
</ul>

<h3>Miscellaneous</h3>
<ul>
  <li><span style="font-weight: bold;">(Bug 4358):</span> Exporting
Together UML2.0 project with an EJB Standard
profile applied to the Java project requires J2EE libraries (<strong>ejb20.jar</strong>,
    <strong>jms.jar</strong>,
etc.), which are not part of the Together installation. Import the
required libraries to avoid problems during code generation.</li>
  <li><span style="font-weight: bold;">(Bug 3207):</span> During a
UML1.4 to UML 2.0 conversion, unidirectional
hyperlinks that may be a result of manual editing of the model files
are lost.<br>
  </li>
  <li><span style="font-weight: bold;">(Bug 3221):</span> During a
UML1.4 to UML 2.0 conversion, activity nodes used
in
several activity graphs are placed in the ReusedElements Activity.</li>
  <li>StarTeam
integration: After checking in newly added modeling resources/elements
when there are no difference between local and repository versions,
team statuses are shown incorrectly (<strong>Conflicting change</strong>
instead of <strong>Current</strong>). To avoid this problem, use <strong>Forced
checkout</strong> to bring status to <strong>Current</strong>.</li>
  <li>Together fails to start and displays message box "JVM terminated. Exit code -1 ..." 
with all the JVM parameters. This can happen when system memory on a particular 
machine is loaded with other running software so that JVM cannot reserve enough 
memory required by the specified parameters. Reduce the values specified for the 
-Xmx and/or -XX:MaxPermSize parameters in the Together.ini file until the JVM 
can start normally. The first parameter affects the amount of data JVM can handle 
at runtime, and the second parameter affects the amount of classes JVM can load.</li>
</ul>
<p><a href="#top">Back
to top</a></p>
</div>
<h2><a name="Capabilities"></a>Together Capabilities</h2>
<p>The default capabilities are different for classic Together Modeling
and the DSL Toolkit. Select <strong>Window</strong> -&gt; <strong>Preferences</strong>,
then select the <strong>General</strong> node and the <strong>Capabilities</strong>
node. You can click the <strong>Advanced</strong> button to
enable/disable capabilities at a more granular level. </p>
<p>The following table lists the Together capabilities that are enabled
and disabled for classic Together Modeling and the DSL Toolkit:</p>
<table border="1" width="985">
  <tbody>
    <tr>
      <td width="106"><strong>Capability group </strong></td>
      <td width="140"><strong>Advanced Capability item </strong></td>
      <td width="528"><strong>Description</strong></td>
      <td width="96"><strong>Classic Together Modeling default </strong></td>
      <td width="81"><strong>DSL Toolkit default </strong></td>
    </tr>
    <tr>
      <td><strong>DSL Development</strong> </td>
      <td>&nbsp;</td>
      <td>Features related to domain-specific language and model-driven
development. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Diagram Definition</strong> </td>
      <td>Diagram definition capabilities for domain models.</td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Domain Modeling</strong> </td>
      <td>Capabilities associated with modeling a domain-specific model.</td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>DSL Project</strong></td>
      <td>General features for working with DSL Projects.</td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td><strong>Model to Model Transformations</strong> </td>
      <td>&nbsp;</td>
      <td>Features for model-to-model transformations. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Operational Mapping Language (QVT)</strong> </td>
      <td>Operational mapping language (QVT) features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Operational QVT Debugging</strong> </td>
      <td>Operational QVT debugging features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td><strong>Model to Text Transformation</strong> </td>
      <td>&nbsp;</td>
      <td>Features for model-to-text transformations. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Template Authoring</strong> </td>
      <td>Template authoring features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Template Exploring</strong> </td>
      <td>Template exploring features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Template Exploring (Legacy)</strong> </td>
      <td>Legacy template exploring. </td>
      <td>Disabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td><strong>Model Workflow</strong> </td>
      <td>&nbsp;</td>
      <td>Features for model workflow. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Workflow Definition</strong> </td>
      <td>Workflow definition features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Workflow Execution</strong> </td>
      <td>Workflow execution features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td><strong>Modeling</strong></td>
      <td>&nbsp;</td>
      <td>Modeling Capabilities.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Business Process Modeling</strong> </td>
      <td>Business Process Modeling.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>C++ Modeling</strong> </td>
      <td>C++ Modeling.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Data Modeling</strong> </td>
      <td>Data Modeling.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Documentation</strong></td>
      <td>Documentation generation.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>IDL Modeling</strong> </td>
      <td>IDL Modeling . </td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Java Modeling</strong> </td>
      <td>Java Modeling </td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Manage element persistence</strong> </td>
      <td>Ability to manage element persistence state, make it
stand-alone or packaged along with other elements in containing package.</td>
      <td>Disabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>MDL and MDX Imports</strong> </td>
      <td>MDL and MDX Imports.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Model QA</strong> </td>
      <td>Model Quality Assurance.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Modeling profiles</strong> </td>
      <td>Profiles.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Patterns</strong></td>
      <td>Patterns Definition and Registry, Patterns Recognition.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Source code QA</strong> </td>
      <td>Source code Quality Assurance</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Together Project Import</strong> </td>
      <td>Import project from one of the previous versions of Together.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Together QVT</strong> </td>
      <td>QVT implementation initially appeared at Together 2006,
primary engine to work with Together models.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>UML 1.4</strong> </td>
      <td>UML 1.4 Modeling.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>UML 2.0</strong> </td>
      <td>UML 2.0 Modeling.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>XMI Import/Export</strong> </td>
      <td>XMI Import/Export.</td>
      <td>Enabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>XSL</strong></td>
      <td>XSL transformations.</td>
      <td>Enabled</td>
      <td>Disabled<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><span style="font-weight: bold;">Enhanced
Rich Text Editor</span><br>
      </td>
      <td style="vertical-align: top;">Enhanced Rich Text Editor for
properties<br>
      </td>
      <td style="vertical-align: top;">Enabled<br>
      </td>
      <td style="vertical-align: top;">Enabled<br>
      </td>
    </tr>
    <tr>
      <td><strong>Modeling Tools</strong> </td>
      <td>&nbsp;</td>
      <td>Features for modeling tools. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Hyperlinks and Requirement Traces (Early Access)</strong>
      </td>
      <td>Hyperlinks and requirement traces features (early access). </td>
      <td>Disabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Model Refactoring (Early Access)</strong> </td>
      <td>Model refactoring features (early access). </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td><strong>Reporting</strong></td>
      <td>&nbsp;</td>
      <td>Features for reporting. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Model Reporting</strong> </td>
      <td>Model reporting features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>Report Definition</strong> </td>
      <td>Report definition features. </td>
      <td>Disabled</td>
      <td>Enabled</td>
    </tr>
    <tr>
      <td><strong>UML Modeling</strong> </td>
      <td>&nbsp;</td>
      <td>Features for UML modeling. </td>
      <td>Disabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>UML2 Diagramming</strong> </td>
      <td>UML2 diagramming features. </td>
      <td>Disabled</td>
      <td>Disabled</td>
    </tr>
    <tr>
      <td>&nbsp;</td>
      <td><strong>UML2 Model Development</strong> </td>
      <td>UML2 model development features. </td>
      <td>Disabled</td>
      <td>Disabled</td>
    </tr>
  </tbody>
</table>
<div>
<h2><a name="finding_out_more"></a>Finding Out More</h2>
</div>
<p><b>Online Help</b></p>
<p>Together provides online help through your Eclipse help browser.
Select <b>Help Contents</b> on the <b>Help</b> menu. When the help
browser opens, click <i>Borland<em><i><sup>&reg;</sup></i></em>
Together<em><i><sup>&reg; </sup></i></em>Modeling Guide</i>, <em><i>Borland<sup>&reg;</sup>
Together<sup>&reg;</sup></i> DSL Toolkit Guide</em>, or other online
help section.</p>
<p><b>Online technical publications</b></p>
<p>The latest versions of Release Notes and product documentation are
published at <a href="http://info.borland.com/techpubs/together/">Together
Technical Publications</a> page</p>
<p><b>Product announcements</b></p>
<p>Together product announcements are available at the <a
 href="http://support.borland.com/community/index.php?t=thread&amp;frm_id=17&amp;">Together
Announcements</a> section of <a
 href="http://support.borland.com/community/">Borland Community</a></p>
<p><b>Product discussion</b></p>
<p>Together product discussion is available at the <a
 href="http://support.borland.com/community/index.php?t=thread&amp;frm_id=15&amp;">Together
Product Discussion</a> section of <a
 href="http://support.borland.com/community/">Borland Community</a></p>
<h2><a name="getting_help"></a>Getting Assistance</h2>
<p>Visit Borland Technical Support at <a
 href="http://support.borland.com/">http://support.borland.com/</a></p>
<p>Visit Borland at <a href="http://www.borland.com/">http://www.borland.com/</a></p>
<p><a href="#top">Back to top</a></p>
<p>&nbsp;</p>
<div style="border-top: 1pt solid silver; font-size: 75%;">Copyright
&copy; 1998-2009 Borland Software Corporation. All Borland brand and
product names are trademarks or registered trademarks of Borland
Software Corporation in the United States and other countries. All
other marks are the property of their respective owners.</div>
</body>
</html>
